Monitoring correctable errors on a bus interface to determine whether to redirect input/output request (i/o) traffic to another bus interface

ABSTRACT

Provided are a computer program product, system, and method for monitoring correctable errors on a bus interface to determine whether to redirect traffic to another bus interface. A processing unit sends Input/Output (I/O) requests from a host to a storage over a first bus interface to a first device adaptor, wherein the first device adaptor provides a first connection to the storage. A determination is made as to whether a number of correctable errors on the first bus interface exceeds an error threshold. The correctable errors are detected and corrected in the first bus interface by hardware of the first bus interface. In response to determining that the number of correctable errors on the first bus interface exceeds the error threshold, at least a portion of I/O requests are redirected to use a second bus interface to connect to a second device adaptor providing a second connection to the storage.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to a computer program product, system, andmethod for monitoring correctable errors on a bus interface to determinewhether to redirect traffic to another bus interface.

2. Description of the Related Art

In a storage environment, a storage system may include redundantprocessors and components that communicate over multiple PeripheralComponent Interconnect Express (PCIe) busses. The PCIe bus technologyprovides error logging and error handling within the PCIe hardware. ThePCIe hardware classifies errors as uncorrectable errors or correctableerrors. Correctable errors may have an impact on performance, such aslatency and bandwidth, but no data/information is lost and the PCIe busremains reliable. Examples of correctable errors include a badtransaction layer packet (TLP) error, such as a bad Link CyclicalRedundancy Check (LCRC) or incorrect sequence number, bad data linklayer packet (DLLP), such as a replay timer timeout receiver error,framing error, etc. Uncorrectable non-fatal errors comprise errors thatdo not have an impact on the integrity of the PCIe bus interface, butdata/information is lost. Non-fatal errors are corrupted transactionsthat cannot be corrected by the bus hardware. Uncorrectable fatal errorsare errors which impact the integrity of the PCIe bus interface suchthat the link is no longer reliable and data is lost. Recovery from afatal error requires resetting the component and link.

There is a need in the art for improved techniques for managing businterface errors.

SUMMARY

Provided are a computer program product, system, and method formonitoring correctable errors on a bus interface to determine whether toredirect traffic to another bus interface. A processing unit sendsInput/Output (I/O) requests from a host to a storage over a first businterface to a first device adaptor, wherein the first device adaptorprovides a first connection to the storage. A determination is made asto whether a number of correctable errors on the first bus interfaceexceeds an error threshold. The correctable errors are detected andcorrected in the first bus interface by hardware of the first businterface. In response to determining that the number of correctableerrors on the first bus interface exceeds the error threshold, at leasta portion of I/O requests are redirected to use a second bus interfaceto connect to a second device adaptor providing a second connection tothe storage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an embodiment of a storage system.

FIG. 2 illustrates an embodiment of a host adaptor in the storagesystem.

FIG. 3 illustrates an embodiment of failover information used todetermine whether to failover to another device adaptor in the storagesystem.

FIG. 4 illustrates an embodiment of operations to perform a failover toanother device adaptor in the storage system.

FIG. 5 illustrates an embodiment of operations to perform a failbackupon correction or repair of errors in a bus interface.

FIG. 6 illustrates an embodiment of operations to process a servicerequest at a processing unit in the storage system.

FIG. 7 illustrates an embodiment of operations for a host adaptor torebalance Input/Output (I/O) request workload in the storage system.

FIG. 8 illustrates an embodiment of operations for a processing unit torebalance Input/Output (I/O) request workload to another processing unitin the storage system.

FIG. 9 illustrates an embodiment of a computer architecture used withdescribed embodiments.

DETAILED DESCRIPTION

In a storage system having redundant bus interfaces, such as PCIe businterfaces, to connect redundant processing units to redundant deviceadaptors and host adaptors, correctable errors may propagate on the businterface as workload increases. Certain operations, such as aconcurrent code load at a processing unit and other operations, mayincrease traffic and the correctable errors on the PCIe bus to the pointthat uncorrectable errors begin occurring, which results in data andinformation loss, as well as fatal uncorrectable errors, which mayresult in eventual loss of access to the components and cessation ofprocessing of I/O requests in the storage system.

Described embodiments provide techniques to handle correctable errors ina storage system having redundant components by redirecting I/O requeststo a different bus interface when a bus interface over which I/Orequests are being transmitted experiences a level of correctable errorsthat increases the likelihood that uncorrectable errors may arise. Someor all of the I/O requests may be redirected by having a processing unittransmit I/O requests on a different bus interface to another deviceadaptor to connect to the storage. Redirecting I/O requests from the businterface experiencing correctable errors allows that bus interface tobe repaired and brought back into use after the problem resulting in thehigh level of correctable errors is fixed.

In further embodiments, the processing units and host adaptors in thesystem may determine whether one bus interface has a high level ofcorrectable errors relative to another bus interface and redirect atleast a portion of the I/O requests to the other bus interface.Relieving I/O traffic on the bus interface experiencing a relativelyhigh level of correctable errors reduces the amount of correctableerrors and reduces the likelihood that the bus interface will experienceuncorrectable errors.

FIG. 1 illustrates an embodiment of a storage controller 100 including aplurality of independent processing units 102 a, 102 b, such as aprocessor complex (CEC), that each have a connection 104 a, 104 b to afirst bus interface 106 a, that connects to a first Input/Output (I/O)bay 108 a and the device adaptors (DA) and hardware adaptors (HA)therein. Each of the processing units 102 a, 102 b have a connection 110a, 110 b to a second bus interface 106 b, that connects to a secondInput/Output (I/O) bay 108 b. The processing units 102 a, 102 b may alsocommunicate with each other directory over a link 112, such as a RemoteI/O (RIO) loop.

Each bus interface 106 a, 106 b includes bus hardware 114 a, 114 b tomanage bus operations and log errors, a bus switch 116 a, 116 b toconnect to adaptor endpoints, including host adaptors (HA) and deviceadaptors (DA) in the I/O bays 108 a, 108 b. A host 120 connects to thestorage controller 100 through a host adaptor 200 ₁ in the I/O bay 108a.

In one embodiment, the bus interfaces 106 a, 106 b may comprisePeripheral Component Interconnect Express (PCIe) bus interfacetechnology, and the bus hardware 114 a, 114 b may comprise the rootcomplex of the PCIe bus. In alternative embodiments, the bus interfaces106 a, 106 b may utilize suitable bus interface technology other thanPCIe.

A disk enclosure 122 includes a plurality of storage devices 124 inwhich logical volumes are configured. Each processing unit 102 a, 102 bis assigned one of the device adaptors in each of the I/O bays 108 a,108 b that connect to the disk enclosure 122 to provide access to dataconfigured in the storage devices 124. Each processing unit 102 a, 102 bhas a default configuration to default communicate with a device adaptor(DA) in one of the I/O bays 108 a, 108 b, where the defaultconfiguration will assign the different processing units 102 a, 102 b todevice adaptors in different of the I/O bays 108 a, 108 b. For instance,in the default configuration, first processing unit 102 a may be defaultassigned device adaptor 126 ₁ in I/O bay 108 a and also assigned aredundant device adaptor 126 ₂ in the other I/O bay 108 a for afailover. The second processing unit 102 b may be default assigneddevice adaptor 126 ₃ in I/O bay 108 b and also assigned a redundantdevice adaptor 126 ₄ in the other I/O bay 108 a for use in a failover.

Each processing unit 102 a, 102 b includes an I/O manager 130 a, 130 bto manage I/O requests from attached hosts to storage space configuredin the storage devices 124 of the disk enclosure 122, and perform otherrelated operations, such as path selection and error handling. Eachprocessing unit 102 a, 102 b further maintains failover information 300a, 300 b providing information on errors collected in the bus interfaces106 a, 106 b used to determine whether to failover from a currently useddevice adaptor (DA) in one of the I/O bays 108 a, 108 b to the other ofthe device adaptors (DA) in the other of the I/O bays 108 b, 108 a.

In the embodiment of FIG. 1, two redundant processing units 102 a, 102b, two bus interfaces 106 a, 106 b and two I/O bays 108 a, 108 b areshown. In further embodiments, there may be more than the number ofshown redundant elements 102 a, 102 b, 106 a, 106 b, 108 a, 108 b, toprovide additional redundancy.

The storage controller 100 may comprise a storage system, such as theInternational Business Machines Corporation (IBM®) DS8000® and DS8880storage systems, or storage controllers and storage systems from othervendors. (IBM and DS8000 are trademarks of International BusinessMachines Corporation throughout the world).

The storage devices 124 in the disk enclosure 122 may comprise differenttypes or classes of storage devices, such as magnetic hard disk drives,solid state storage device (SSD) comprised of solid state electronics,EEPROM (Electrically Erasable Programmable Read-Only Memory), flashmemory, flash disk, Random Access Memory (RAM) drive, storage-classmemory (SCM), etc., Phase Change Memory (PCM), resistive random accessmemory (RRAM), spin transfer torque memory (STM-RAM), conductivebridging RAM (CBRAM), magnetic hard disk drive, optical disk, tape, etc.Volumes in a storage space may further be configured from an array ofdevices, such as Just a Bunch of Disks (JBOD), Direct Access StorageDevice (DASD), Redundant Array of Independent Disks (RAID) array,virtualization device, etc. Further, the storage devices 124 in the diskenclosure 122 may comprise heterogeneous storage devices from differentvendors and different types of storage devices, such as a first type ofstorage devices, e.g., hard disk drives, that have a slower datatransfer rate than a second type of storage devices, e.g., SSDs.

The components, such as the I/O managers 130 a, 130 b, host adaptors(HA), and device adaptors (DA) may be implemented in computer readableprogram instructions in a computer readable storage medium executed by aprocessor and/or computer hardware, such as an Application SpecificIntegrated Circuit (ASIC).

FIG. 2 illustrates an embodiment of one of the host adaptors (HA) 200_(i) in the I/O bays 108 a, 108 b, and includes an I/O manager 202 tomanage I/O requests received from connected hosts to route to one of theprocessing units 102 a, 102 b, and to return requested data to theconnected host 120. The host adaptor 200 _(i) may further maintain aninstance of the failover information 300 _(HA) to use to determinewhether to redirect traffic from one processing unit 102 a to the other102b.

FIG. 3 illustrates an embodiment of the failover information 300—such asthe instances of failover information 300 ₁, 300 ₂, 300 _(HA), andincludes for each bus interface, e.g. 106 a, 106 b, a number ofcorrectable errors 302 ₁ . . . 302 _(n) for n respective bus interfaces,e.g., 106 a, 106 b, measured within a time period. A correctible errormay comprise an error detected and logged in the bus hardware 114 a, 114b of the bus interfaces 106 a, 106 b that may be corrected in the bushardware 114 a, 114 b.

The failover information 300 _(i) further includes an error threshold304 and an interface difference error threshold 306. The error threshold304 is used to determine whether the number of correctable errors 302_(i) for a bus interface reaches a sufficient number such thatuncorrectable errors are likely to soon result. The bus interface 106 a,106 b may operate with a certain number of correctable errors. However,if the correctable errors increase beyond the error threshold 304, thenthe burden on the bus hardware 114 a, 114 b to error correct correctableerrors may result in uncorrectable errors. The interface differenceerror threshold 306 is used to determine whether a difference in thenumber of correctable errors e.g., 302 ₁ and 302 ₂, between two businterfaces, e.g., 106 a, 106 b, is of a sufficient amount to triggerload balancing to redirect I/O requests from the bus interface 106 a,106 b having the greater number of correctable errors to the other businterface, e.g., 106 b, 106 a, having fewer correctable errors.

FIG. 4 illustrates an embodiment of operations performed by the I/Omanager 130 a, 130 b in one of the processing units 102 a, 102 b toinitiate a failover procedure. Upon initiating (at block 400) operationsto determine whether to initiate a failover, the I/O manager 130 a, 130b polls (at block 502) the bus hardware 114 a, 114 b to determine anumber of correctable errors on the bus 106 a, 106 b. The determinednumber of correctable errors is added (at block 404) to the number ofcorrectable errors 302 ₁ . . . 302 _(n) for each polled bus interface106 a, 106 b. The number of correctable errors 302 ₁ . . . 302 _(n)number may be periodically cleared, such that the number of correctableerrors 302 ₁ . . . 302 _(n) is incremented after multiple pollingoperations until cleared, or the number of correctable errors 302 ₁ . .. 302 _(n) may be set to the determined number upon each determination.

If (at block 406) the number of correctable errors 302 _(i), for the businterface 106 a, 106 b to the I/O bay 108 a, 108 b having the defaultdevice adaptor (DA), e.g., 126 ₁, 126 ₃, being used, exceeds the errorthreshold 304, then a determination is made (at block 408) whether thereis an additional bus interface 106 a, 106 b to an additional I/O bay 108a, 108 b not yet considered for failover. If so, then the I/O manager130 a, 130 b selects (at block 410) one of the at least one additionalbus interface 106 a, 106 b to an I/O bay 108 a, 108 b, not yetconsidered. The number of correctible errors 302 _(i) for the selectedbus interface 106 a, 106 b are determined (at block 412) and adetermination is made (at block 414) whether to failover to a deviceadaptor (DA), e.g., 126 ₂, 126 ₄, on the additional I/O bay 108 a, 108 bbased on the number of correctable errors 302 ₁ for the selected businterface 106 a, 106 b. If (at block 414) a determination is made tofailover, then the I/O manager 130 a, 130 b redirects (at block 416) atleast a portion of I/O requests, e.g., failover, to a device adaptor(DA) 126 ₂, 126 ₄, in the additional I/O bay 108 a, 108 b connected tothe selected additional bus interface 106 a, 106 b, to connect tostorage space configured in the storage devices 124 in the diskenclosure 122. In performing the redirecting of I/O requests, some orall of the I/O requests may be redirected. In an embodiment where thepath through the bus interface 106 a, 106 b experiencing the correctableerrors will be repaired, all the I/O requests may be redirected to theother device adaptor. Upon failing over to the new device adaptor,repairs may be initiated on the bus interface 106 a, 106 b on which thecorrectible errors were experienced resulting in the failover, such asresetting the bus interface 106 a, 106 b or performing otherreconfiguration operations. If (at block 406) the number of correctableerrors 302 _(i) for the active bus interface 106 a, 106 b does notexceed the error threshold 304 or if (at block 408) there are no furtheradditional bus interfaces to consider for failover, then control endswithout failing over to a device adaptor in another I/O bay 108 a, 108 bover a different bus interface 106 a, 106 b than currently being used.

In one embodiment, the determination at block 414 may determine whetherthe number correctable errors 302 _(i) for the selected bus interface106 a, 106 b, being considered for failover, exceeds the error threshold304, so that failover will not occur to the selected bus interface 106a, 106 b if the selected bus interface 106 a, 106 b is also experiencinga high level of correctible errors also likely to result inuncorrectable errors occurring. In a further embodiment, thedetermination at block 414 may consider whether a difference in thenumber of correctable errors between the current active bus interface106 a, 106 b and the selected bus interface exceeds the error differencethreshold 306 to warrant failing over to another device adaptor (DA),e.g., 126 ₂, 126 ₄, in the I/O bay 108 a, 108 b connected to theselected bus interface 106 a, 106 b. For instance, if the difference incorrectable errors does not exceed the threshold 306, then failing overmay not be desirable because the difference in the number of correctableerrors between the bus interface 106 a, 106 b experiencing the highlevel of correctable errors is not sufficient to allow the other businterface 106 a, 106 b to absorb the redirected traffic without alsoexperiencing uncorrectable errors.

With the embodiments of FIG. 4, a processing unit 102 a, 102 b maydetermine to failover to a device adaptor in a different I/O bay 108 a,108 b upon determining that correctable errors exceed a threshold, eventhough such correctable errors are not affecting the reliability of thebus interface 106 a, 106 b and data integrity of data transmitted overthe bus interface 106 a, 106 b. However, once the error threshold isexceeded, there is a desire to redirect I/O requests from the businterface 106 a, 106 b experiencing the relatively high number ofcorrectable errors as a preventive measure to avoid correctable errorsincreasing to a level to cause burdens resulting in uncorrectableerrors.

FIG. 5 illustrates an embodiment of operations performed by an I/Omanager 130 a, 130 b at the processing units 102 a, 102 b to failbackafter completing repairing errors and/or performing maintenance on thebus interface 106 a, 106 b experiencing more than the error threshold304 number. Upon (at block 500) completing repairing a bus interface 106a, 106 b, such as one repaired at block 418 in FIG. 4, a determinationis made as to whether a failover occurred with respect to the repairedbus interface 106 a, 106 b. If so, then a failback is performed (atblock 504) from the device adaptor in the I/O bay 108 a, 108 b currentlybeing used to the default device adaptor (DA) in the I/O bay 108 a, 108b connected to the repaired bus interface 106 a, 106 b or components.The number of correctible errors 302 _(i) for the repaired bus interface106 a, 106 b may then be cleared to re-accumulate.

With the operations of FIG. 5, after repairing a bus interface 106 a,106 b that was the subject of a failover, a failback may be performedfor the processing unit 102 a, 102 b to return to using the defaultdevice adaptor in the I/O bay 108 a, 108 b to which the repaired businterface 106 a, 106 b connects. This provides a balancing of theworkload by returning to the default device adaptor because after thefailover, both processing units 102 a, 102 b would be directing I/Orequests toward the surviving I/O bay 108 a, 108 b using the same businterface 106 a, 106 b. Returning the processing unit 102 a, 102 b tousing its default device adaptor on the repaired bus interface 106 a,106 b and I/O bay 108 a, 108 b rebalances the workload across both businterfaces 106 a, 106 b, which further reduces the likelihood thatcorrectible errors will transform into uncorrectable errors.

FIG. 6 illustrates an embodiment of operations performed by the I/Omanager 130 a, 130 b at a processing unit 102 a, 102 b receiving aservice request to perform a service operation, such as a code loadupdate, repairing of a component in the processing unit 102 a, 102 b, ora repair/update operation for the I/O bay 108 a, 108 b or device adaptor(DA) the processing unit 102 a, 102 b is currently using after thefailover. Upon receiving (at block 602) the service request, the I/Omanager 130 a, 130 b determines (at block 602) whether there has been afailover at the processing unit 102 a, 102 b, such that I/O requests arebeing redirected on another bus interface 106 a, 106 b to a non-defaultassigned device adaptor. If (at block 602) there was a failover, thenthe service request is failed (at block 604), otherwise, if there was nofailover, then the service request is allowed to proceed (at block 606).

With the described embodiments of FIG. 6, the service request is failedif there has been a failover to avoid additional load on the processingunit 102 a, 102 b and the failover bus interface 106 a, 106 b beingused, because during failover, some or all of the I/O requests for bothprocessing units 102 a, 102 b are being redirected to the surviving businterface 106 a, 106 b and I/O bay 108 a, 108 b, or limited number ofsuch components. Adding further load during the failover could increasethe number of correctable errors experienced on the sole surviving businterface 106 a, 106 b being used, which could result in uncorrectableerrors, which would impair the integrity of the sole or limited numberof surviving bus interface 106 a, 106 b.

FIG. 7 illustrates an embodiment of operations performed by the I/Omanager 202 at the host adaptor 200 ₁, e.g., host adaptor 200 ₁, todetermine whether to perform a load balancing operation to redirect aportion of host I/O requests to the other processing unit 102 a, 102 b.In one embodiment, the initial configuration would be for host adaptors(HAs) in an I/O bay to direct I/O requests to the processing unit 102 a,102 b having a default assigned device adaptor (e.g., 126 ₁, 126 ₃) inthe I/O bay 108 a, 108 b of the host adaptor (HA). Upon initiating (atblock 700) load balancing operations, the host adaptor I/O manager 202performs operations 402 and 404 in FIG. 4 to update correctable errorsfor the bus interface 106 a or 106 b connecting to the I/O bay 108 a or108 b including the host adaptor 200 _(i) and for other bus interfaces106 a or 106 b connecting to I/O bays 108 a or 108 b not including thehost adaptor 200 _(i) performing the operations of FIG. 7. The I/Omanager 202 may determine the number of correctible errors 302 _(i) forbus interfaces 106 a, 106 b, such as those not connected to the I/O bay108 a, 108 b including the host adaptor 200 ₁, by sending messages tothe processing units 102 a, 102 b for their failover information 300 ₁,300 ₂. If (at block 704) there is an additional bus interface 106 a, 106b to an additional non-default processing unit 102 a, 102 b not alreadyconsidered, then the I/O manager 202 determines the number ofcorrectible errors on the active bus interface 106 a or 106 b connectingto the I/O bay 108 a, 108 b including the host adaptor 200 _(i) and thenumber of correctible errors on the selected bus interface connecting toanother I/O bay 108 b, 108 a.

If (at block 710) the difference of the number of correctible errors onthe bus interface connecting to the host adaptor 200 _(i) and theselected other bus interface exceed the difference threshold 306, thenthe host adaptor I/O manager 202 directs (at block 712) a first portionof I/O requests over the bus interface 106 a or 106 b, connecting to thehost adaptor 200 _(i), to the default processing unit 102 a or 102 b anddirects (at block 714) a second portion of the I/O requests over the businterface 106 a or 106 b connecting to the host adaptor 200 _(i) to anon-default assigned processing unit 102 a or 102 b. The non-defaultprocessing unit 102 a or 102 b in turn would send the I/O requests overthe selected bus interface 106 a, 106 b to an I/O bay 108 a, 108 b notincluding the host adaptor 200 _(i) initiating the redirecting of thesecond portion of the I/O requests. If (at block 710) the difference ofthe number of correctible errors does not exceed the differencethreshold 306, then control proceeds back to block 704 to determine ifthere is an additional bus interface to consider, in implementationshaving more than two redundant bus interfaces 106 a, 106 b. If (at block704) there are no additional bus interfaces to consider, then controlends without rebalancing the workload among the processing units 102 a,102 b.

With the embodiment of FIG. 7, a host adaptor may rebalance I/O requestworkload by directing a portion of the I/O requests to a non-defaultprocessor 102 a, 102 b that sends I/O requests to the storage 124 over abus interface 106 a, 106 b and I/O bay 108 a, 108 b not connected to thehost adaptor 200 _(i). This rebalancing reduces traffic on the businterface 106 a, 106 b having a significantly greater number ofcorrectable errors by redirecting I/O traffic to a non-defaultprocessing unit 102 a, 102 b using a bus interface 106 a, 106 b having athreshold number of fewer errors. Reducing traffic on a bus interface106 a, 106 b having a higher relative number of correctable errors thanother bus interfaces reduces the likelihood that the correctable errorson the bus interface 106 a, 106 b will reach a level that results inuncorrectable errors.

FIG. 8 illustrates an embodiment of operations performed by the I/Omanagers 130 a, 130 b in the processing units 102 a, 102 b to perform aload balancing operation to redirect a portion of host I/O requests tothe other processing unit 102 a, 102 b. Upon (at block 800) one of theI/O managers 130 a, 130 b initiating operations to shift some of theload of I/O requests to the other processing unit, the I/O managerperforms (at block 802) the operations at blocks 702 through 710 in FIG.7 to determine whether to redirect a portion of the I/O requests toanother processing unit using a selected additional bus interface,different from the bus interface 106 a, 106 b used by the processingunit 102 a, 102 b to connect to the default assigned device adaptor. TheI/O manager 130 a, 130 b processes a first portion of the I/O requestslocally, transferring over the bus interface 106 a, 106 b to the defaultdevice adaptor 126 ₁, 126 ₃. The I/O manager 130 a, 130 b transmits (atblock 806) the second portion of the I/O requests to another processingunit 102 a, 102 b to process, via the direct processor link 112 orconnecting bus interface 106 a, 106 b, such as first processing unit 102a sending the second portion of I/O requests over link 104 a or throughbus interface 106 a via link 104 b to the second processing unit 102 b.

With the embodiment of FIG. 8, one of the processing units 102 a, 102 bmay rebalance I/O request workload by directing a portion of the I/Orequests to another processor 102 a, 102 b that sends I/O requests tothe storage 124 over a different bus interface 106 b, 106 a from the businterface 106 a, 106 b used by the processing unit 102 a, 102 bperforming the load balancing. This rebalancing reduces traffic on thebus interface 106 a, 106 b having a significantly greater number ofcorrectable errors by redirecting I/O traffic to the other processingunit 102 a, 102 b using a different bus interface 106 a, 106 b havingfewer errors. Reducing traffic on a bus interface 106 a, 106 b having ahigher relative number of correctable errors than other bus interfacesreduces the likelihood that the correctable errors on the bus interface106 a, 106 b will reach a level that results in uncorrectable errors.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Java, Smalltalk, C++ or the like,and conventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The computational components of FIG. 1, including the processing units102 a, 102 b and host 120 may be implemented in one or more computersystems, such as the computer system 902 shown in FIG. 9. Computersystem/server 902 may be described in the general context of computersystem executable instructions, such as program modules, being executedby a computer system. Generally, program modules may include routines,programs, objects, components, logic, data structures, and so on thatperform particular tasks or implement particular abstract data types.Computer system/server 902 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 9, the computer system/server 902 is shown in the formof a general-purpose computing device. The components of computersystem/server 902 may include, but are not limited to, one or moreprocessors or processing units 904, a system memory 906, and a bus 908that couples various system components including system memory 906 toprocessor 904. Bus 908 represents one or more of any of several types ofbus structures, including a memory bus or memory controller, aperipheral bus, an accelerated graphics port, and a processor or localbus using any of a variety of bus architectures. By way of example, andnot limitation, such architectures include Industry StandardArchitecture (ISA) bus, Micro Channel Architecture (MCA) bus, EnhancedISA (EISA) bus, Video Electronics Standards Association (VESA) localbus, and Peripheral Component Interconnects (PCI) bus.

Computer system/server 902 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 902, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 906 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 910 and/or cachememory 912. Computer system/server 902 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 913 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 908 by one or more datamedia interfaces. As will be further depicted and described below,memory 906 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 914, having a set (at least one) of program modules 916,may be stored in memory 906 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. The components of the computer 902 may be implemented asprogram modules 916 which generally carry out the functions and/ormethodologies of embodiments of the invention as described herein. Thesystems of FIG. 1 may be implemented in one or more computer systems902, where if they are implemented in multiple computer systems 902,then the computer systems may communicate over a network.

Computer system/server 902 may also communicate with one or moreexternal devices 918 such as a keyboard, a pointing device, a display920, etc.; one or more devices that enable a user to interact withcomputer system/server 902; and/or any devices (e.g., network card,modem, etc.) that enable computer system/server 902 to communicate withone or more other computing devices. Such communication can occur viaInput/Output (I/O) interfaces 922. Still yet, computer system/server 902can communicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 924. As depicted, network adapter 924communicates with the other components of computer system/server 902 viabus 908. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 902. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

The terms “an embodiment”, “embodiment”, “embodiments”, “theembodiment”, “the embodiments”, “one or more embodiments”, “someembodiments”, and “one embodiment” mean “one or more (but not all)embodiments of the present invention(s)” unless expressly specifiedotherwise.

The terms “including”, “comprising”, “having” and variations thereofmean “including but not limited to”, unless expressly specifiedotherwise.

The enumerated listing of items does not imply that any or all of theitems are mutually exclusive, unless expressly specified otherwise.

The terms “a”, “an” and “the” mean “one or more”, unless expresslyspecified otherwise.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or moreintermediaries.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Onthe contrary a variety of optional components are described toillustrate the wide variety of possible embodiments of the presentinvention.

When a single device or article is described herein, it will be readilyapparent that more than one device/article (whether or not theycooperate) may be used in place of a single device/article. Similarly,where more than one device or article is described herein (whether ornot they cooperate), it will be readily apparent that a singledevice/article may be used in place of the more than one device orarticle or a different number of devices/articles may be used instead ofthe shown number of devices or programs. The functionality and/or thefeatures of a device may be alternatively embodied by one or more otherdevices which are not explicitly described as having suchfunctionality/features. Thus, other embodiments of the present inventionneed not include the device itself.

The foregoing description of various embodiments of the invention hasbeen presented for the purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseform disclosed. Many modifications and variations are possible in lightof the above teaching. It is intended that the scope of the invention belimited not by this detailed description, but rather by the claimsappended hereto. The above specification, examples and data provide acomplete description of the manufacture and use of the composition ofthe invention. Since many embodiments of the invention can be madewithout departing from the spirit and scope of the invention, theinvention resides in the claims herein after appended.

1-24. (canceled)
 25. A computer program product for managing businterface errors in a storage system coupled to a host and storage, thecomputer program product comprising a computer readable storage mediumhaving computer readable program code embodied therein that isexecutable to perform operations, the operations comprising: determiningwhether a number of correctable errors on a first bus interface exceedsan error threshold; in response to determining that the number ofcorrectable errors on the first bus interface exceeds the errorthreshold, performing a failover to redirect Input/Output (I/O) requestsfrom a first device adaptor receiving I/O requests from a host over thefirst bus interface to the storage to use a second bus interface toconnect to a second device adaptor providing a second connection to thestorage; and indicating a repair of at least one of the first businterface and in response to failing over to the second device adaptor.26. The computer program product of claim 25, wherein the second businterface connects a processing unit to the second device adaptor,wherein the number of correctable errors comprises a first number ofcorrectable errors, wherein the operations further comprise: determininga second number of correctible errors on the second bus interface inresponse to determining that the first number of correctable errorsexceeds the error threshold; and determining, based on the second numberof correctable errors, whether to perform the failover to redirect theI/O requests on the second bus interface, wherein the failover toredirect the I/O requests to the second bus interface is performed inresponse to determining to perform the failover to redirect based on thesecond number of correctible errors.
 27. The computer program product ofclaim 26, wherein the determining of whether to perform the failover toredirect based on the second number of correctible errors determines toperform the failover to redirect in response to determining that thesecond number of correctable errors does not exceed the error threshold,wherein the failover to redirect is not performed in response todetermining that the second number of correctable errors exceeds theerror threshold.
 28. The computer program product of claim 26, whereinthe determining of whether to perform the failover to redirect based onthe second number of correctible errors determines to perform thefailover to redirect in response to determining that a difference of thefirst number of correctable errors and the second number of correctableerrors exceeds a difference threshold, wherein the failover to redirectis not performed in response to determining that the difference of thefirst number of correctable errors and the second number of correctableerrors does not exceed the error threshold.
 29. The computer programproduct of claim 25, wherein the operations further comprise: failingback from the second device adaptor to the first device adaptor inresponse to determining that the repair completed.
 30. The computerprogram product of claim 29, wherein a processing unit is assigned thefirst device adaptor in a default assignment, and wherein the failingback from the second device adaptor to the first device adaptorcomprises failing back to the default assignment.
 31. The computerprogram product of claim 25, wherein the error threshold comprises apoint beyond which a number of the correctable errors would result inuncorrectable errors.
 32. A system for managing bus interface errorscoupled to a host and storage, comprising: a processing unit; a firstbus interface; a second bus interface; a first device adaptor; a seconddevice adaptor; a computer readable storage medium having computerreadable program code executed by the processing unit to performoperations, the operations comprising: determining whether a number ofcorrectable errors on the first bus interface exceeds an errorthreshold; in response to determining that the number of correctableerrors on the first bus interface exceeds the error threshold,performing a failover to redirect Input/Output (I/O) requests from thefirst device adaptor receiving I/O requests from the host over the firstbus interface to the storage to use the second bus interface to connectto the second device adaptor providing a second connection to thestorage; and indicating a repair of at least one of the first businterface and in response to failing over to the second device adaptor.33. The system of claim 32, wherein the processing unit comprises afirst processing unit, wherein the second bus interface connects asecond processing unit to the second device adaptor, wherein the numberof correctable errors comprises a first number of correctable errors,wherein the operations further comprise: determining a second number ofcorrectible errors on the second bus interface in response todetermining that the first number of correctable errors exceeds theerror threshold; and determining, based on the second number ofcorrectable errors, whether to perform the failover to redirect the I/Orequests on the second bus interface, wherein the failover to redirectthe I/O requests to the second bus interface is performed in response todetermining to perform the failover to redirect based on the secondnumber of correctible errors.
 34. The system of claim 33, wherein thedetermining of whether to perform the failover to redirect based on thesecond number of correctible errors determines to perform the failoverto redirect in response to determining that the second number ofcorrectable errors does not exceed the error threshold, wherein thefailover to redirect is not performed in response to determining thatthe second number of correctable errors exceeds the error threshold. 35.The system of claim 33, wherein the determining of whether to performthe failover to redirect based on the second number of correctibleerrors determines to perform the failover to redirect in response todetermining that a difference of the first number of correctable errorsand the second number of correctable errors exceeds a differencethreshold, wherein the failover to redirect is not performed in responseto determining that the difference of the first number of correctableerrors and the second number of correctable errors does not exceed theerror threshold.
 36. The system of claim 32, wherein the operationsfurther comprise: failing back from the second device adaptor to thefirst device adaptor in response to determining that the repaircompleted.
 37. The system of claim 36, wherein a processing unit isassigned the first device adaptor in a default assignment, and whereinthe failing back from the second device adaptor to the first deviceadaptor comprises failing back to the default assignment.
 38. Thecomputer program product of claim 32, wherein the error thresholdcomprises a point beyond which a number of the correctable errors wouldresult in uncorrectable errors.
 39. A method for managing bus interfaceerrors in a storage system coupled to a host and storage, comprising:determining whether a number of correctable errors on the first businterface exceeds an error threshold; in response to determining thatthe number of correctable errors on the first bus interface exceeds theerror threshold, performing a failover to redirect Input/Output (I/O)requests from the first device adaptor receiving I/O requests from thehost over the first bus interface to the storage to use the second businterface to connect to the second device adaptor providing a secondconnection to the storage; and indicating a repair of at least one ofthe first bus interface and in response to failing over to the seconddevice adaptor.
 40. The method of claim 39, wherein the processing unitcomprises a first processing unit, wherein the second bus interfaceconnects a second processing unit to the second device adaptor, whereinthe number of correctable errors comprises a first number of correctableerrors, further comprising: determining a second number of correctibleerrors on the second bus interface in response to determining that thefirst number of correctable errors exceeds the error threshold; anddetermining, based on the second number of correctable errors, whetherto perform the failover to redirect the I/O requests on the second businterface, wherein the failover to redirect the I/O requests to thesecond bus interface is performed in response to determining to performthe failover to redirect based on the second number of correctibleerrors.
 41. The method of claim 40, wherein the determining of whetherto perform the failover to redirect based on the second number ofcorrectible errors determines to perform the failover to redirect inresponse to determining that the second number of correctable errorsdoes not exceed the error threshold, wherein the failover to redirect isnot performed in response to determining that the second number ofcorrectable errors exceeds the error threshold.
 42. The method of claim40, wherein the determining of whether to perform the failover toredirect based on the second number of correctible errors determines toperform the failover to redirect in response to determining that adifference of the first number of correctable errors and the secondnumber of correctable errors exceeds a difference threshold, wherein thefailover to redirect is not performed in response to determining thatthe difference of the first number of correctable errors and the secondnumber of correctable errors does not exceed the error threshold. 43.The method of claim 39, further comprising: failing back from the seconddevice adaptor to the first device adaptor in response to determiningthat the repair completed.
 44. The computer program product of claim 32,wherein the error threshold comprises a point beyond which a number ofthe correctable errors would result in uncorrectable errors.